MOCKUP: New modal for inspect IK from motion plan replay - #889
Draft
Marcus (sucrammal) wants to merge 1 commit into
Draft
MOCKUP: New modal for inspect IK from motion plan replay#889Marcus (sucrammal) wants to merge 1 commit into
Marcus (sucrammal) wants to merge 1 commit into
Conversation
|
Contributor
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
Failed motion plans export as request-only JSON, so uploading one into the replayer dead-ends at "No trajectory — nothing to replay" with no way to see why it failed. This mocks up the UI for Dan's upcoming RDK inspect-ik endpoint (APP-17415), which returns every candidate IK solution classified green/yellow/red, so we can settle the UX before the endpoint exists.
Throwaway — the whole thing is a demo.
inspect-ik-client.tsignores the plan you click and always returns a bundled pirouette request + solutions pair, because the two have to describe the same scene for the poses to be drawable. Everything downstream consumesInspectIKResult, so swapping in the real route means replacing that one file.Usage
pnpm devand upload any plan JSON — a failed one like...-err-touch-pickup.jsonis the realistic case, but the mock ignores what you pick